!!! [v6r10] Changes for InnoDB schema #1731
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to accomodate the use of a trigger to generate the TaskID instead of using the mysql AUTO_INCREMENT. Changes to TransformationDB.sql in order to move the schema to InnoDB
phase to ensure full compatibility between different versions of the MySQL DB schema
Contributor
|
I just realized that, in order to ensure full compatibility, we need to port this (or at least the changes to the TransformationDB.py code) to v6r9: done it in #1735 |
Contributor
|
There are conflicts in this PR. Please, resolve. |
Contributor
|
Superseeded by #1738 |
atsareg
pushed a commit
that referenced
this pull request
Dec 2, 2013
Replacement of #1731 with conflicts solved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes to TransformationDB.sql in order to move the schema to InnoDB
Changes to TransformationDB.py -> addTaskForTransformation()
to accomodate the use of a trigger to generate the TaskID instead of using the mysql AUTO_INCREMENT.